[ZEPPELIN-1489] Remove jdbc-like interpreter example properties and improve JDBC docs #1480
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR for?
Currently we can use
%jdbc(prefix)for multi database connections(e.g. configuring both postgresql and hive in one JDBC interpreter). But after #1360 merged, Zeppelin doesn't support%jdbc(prefix)to%prefixanymore. So auto-prefix feature is not working for%jdbc(prefix). The auto-prefix only works for%prefixnow. Considering this status, it would be better we remove the JDBC connection examples injdbc/interpreter-setting.json(this is come from #1096) so that users can create several JDBC interpreters instead of using multiple connections with one JDBC interpreter. I removed the related contents injdbc.mdas well.Also, the contents of current JDBC documentation page is quite confusing and unorganized. So I updated the contents with some screenshot images to guide "How to create JDBC interpreter", "How to edit the interpreter properties for the connection", "How to use
%prefixwith the interpreter", and so on.What type of PR is it?
Improvement & Documentation
What is the Jira issue?
ZEPPELIN-1489
How should this be tested?
interpreter-setting.jsonmvn clean package -DskipTests -Pspark-1.6 -pl 'jdbc,zeppelin-interpreter,zeppelin-web,zeppelin-server,zeppelin-zengine,zeppelin-display'docs/dir as described in hereinterpreter -> JDBCand just compare this locally builded page with the original JDBC pageScreenshots (if appropriate)
Since many contents are changed, it would be better to build
docs/locally to review all of the change.
### Questions: - Does the licenses files need update? no - Is there breaking changes for older versions? no - Does this needs documentation? yes